Don't use g_slist_next in gdk
authorMatthias Clasen <mclasen@redhat.com>
Tue, 20 Oct 2015 00:28:06 +0000 (20:28 -0400)
committerMatthias Clasen <mclasen@redhat.com>
Tue, 20 Oct 2015 10:14:57 +0000 (06:14 -0400)
We generally just use ->next directly.

gdk/gdkevents.c
gdk/gdkwindow.c

index 4052d54bd8561fb7d5d98c7d0991bee00dce0bf4..ed649130fc5b18b9726b7109cff7cf51f46d085a 100644 (file)
@@ -108,7 +108,7 @@ _gdk_event_queue_find_first (GdkDisplay *display)
             return tmp_list;
         }
 
-      tmp_list = g_list_next (tmp_list);
+      tmp_list = tmp_list->next;
     }
 
   return NULL;
index 75d1034b7a0259d4182abbab38bd90625fac95c5..9206ead6712306eb65b2778fd992c71e262a137d 100644 (file)
@@ -7712,8 +7712,8 @@ find_common_ancestor (GdkWindow *win1,
   while (list1 && list2 && (list1->data == list2->data))
     {
       tmp = list1->data;
-      list1 = g_list_next (list1);
-      list2 = g_list_next (list2);
+      list1 = list1->next;
+      list2 = list2->next;
     }
   g_list_free (path1);
   g_list_free (path2);
@@ -8083,7 +8083,7 @@ _gdk_synthesize_crossing_events (GdkDisplay                 *display,
          while (list)
            {
              win = list->data;
-             list = g_list_next (list);
+             list = list->next;
              if (list)
                next = list->data;
              else